Skip to content

feat(OpenAI): add Conversation API #658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

feat(OpenAI): add Conversation API #658

wants to merge 2 commits into from

Conversation

iBotPeaches
Copy link
Collaborator

@iBotPeaches iBotPeaches commented Aug 26, 2025 •
edited
Loading

What:

  • Bug Fix
  • New Feature

Tasks

  • Add endpoints (Conversations)
  • Add endpoints (Conversation Files)
  • Fix README
  • Adjust Conversations to be root-level entity
  • Test with real samples
  • Migrate Response Items (Retrieve, ListInputItems, Create) into Actions to be re-usable for Conversation Items
  • Migrate Response Output into Action
  • Migrate Response Tool Choice into Action
  • Migrate Response Tools into Action
  • Migrate Response Output Text into Action
  • Add Tests
  • Add Fixtures

Crossed off things being handled in #671

Description:

Adds Conversation API and Conversation Item API. All endpoints were tested via this sample script.

@iBotPeaches
Copy link
Collaborator Author

I originally designed this under Response API, because this is all its used for at present, but the URL structure of the endpoints does not sit under /responses like say Vector Files or Container Files. So now I believe its a new top level entity, but all its payload/responses are chunks of Response API.

@mydnic
Copy link

mydnic commented Sep 1, 2025

I originally designed this under Response API, because this is all its used for at present, but the URL structure of the endpoints does not sit under /responses like say Vector Files or Container Files. So now I believe its a new top level entity, but all its payload/responses are chunks of Response API.

Isn't this the replacement of the old Threads API ? I believe the Conversations API is required to be able to migrate from Assistants/Threads/Runs API to the Response API

@iBotPeaches
Copy link
Collaborator Author

Isn't this the replacement of the old Threads API ? I believe the Conversations API is required to be able to migrate from Assistants/Threads/Runs API to the Response API

Screenshot From 2025-09-01 06-38-35

Yes thats correct.

@iBotPeaches iBotPeaches mentioned this pull request Sep 1, 2025
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@iBotPeaches @mydnic